Dinastycoin Blockchain Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Autorefresh is OFF

Tx hash: 8fa27ad20878b9fc9816a259d934d470f7be301deb226f4462a235882d77f582

Tx prefix hash: a77ca32328dcf56e623f1abe0a030be7f94f0ce3d3339f669dc221b02f49db63
Tx public key: 4e9eafc8789bdb92b8d868af2cbb3f02694cad2c9b540e15b34adc64864db39c
Timestamp: 1706765924 Timestamp [UCT]: 2024-02-01 05:38:44 Age [y:d:h:m:s]: 01:067:02:05:38
Block: 947812 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 309021 RingCT/type: yes/0
Extra: 014e9eafc8789bdb92b8d868af2cbb3f02694cad2c9b540e15b34adc64864db39c02110000000259dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 18cf585627589f6b8c08fbbb4a1e80e359676d744799e6df596043dce63ebb84 0.600000000000 1406170 of 15

Check which outputs belong to given Dinastycoin address/subaddress and viewkey

For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side



Prove to someone that you have sent them Dinastycoin in this transaction

Tx private key can be obtained using get_tx_key command in dinasty-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side



{ "version": 2, "unlock_time": 947822, "vin": [ { "gen": { "height": 947812 } } ], "vout": [ { "amount": 600000000, "target": { "key": "18cf585627589f6b8c08fbbb4a1e80e359676d744799e6df596043dce63ebb84" } } ], "extra": [ 1, 78, 158, 175, 200, 120, 155, 219, 146, 184, 216, 104, 175, 44, 187, 63, 2, 105, 76, 173, 44, 155, 84, 14, 21, 179, 74, 220, 100, 134, 77, 179, 156, 2, 17, 0, 0, 0, 2, 89, 218, 211, 245, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8