Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c41d7156a91541e36c67045cb902bbd94fde54a07d812fa52351945cbfc04052

Tx prefix hash: 4f556090a294ab1bc6de0ded4f2224f7d05bd5fdf1f1362b81248eb1059b9132
Tx public key: 830bcc3fb9662bb0cdc50f2eaa6b4a85a812ea0038c1dcbe3515a44aebc6ac7d
Timestamp: 1728432676 Timestamp [UCT]: 2024-10-09 00:11:16 Age [y:d:h:m:s]: 00:046:14:00:55
Block: 1127465 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 33273 RingCT/type: yes/0
Extra: 01830bcc3fb9662bb0cdc50f2eaa6b4a85a812ea0038c1dcbe3515a44aebc6ac7d02110000000791e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 784871f4e3725d06d862dadf8ea69f9716218c330b1618a7c55af4357a161fdf 0.600000000000 1610270 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": 1127475, "vin": [ { "gen": { "height": 1127465 } } ], "vout": [ { "amount": 600000000, "target": { "key": "784871f4e3725d06d862dadf8ea69f9716218c330b1618a7c55af4357a161fdf" } } ], "extra": [ 1, 131, 11, 204, 63, 185, 102, 43, 176, 205, 197, 15, 46, 170, 107, 74, 133, 168, 18, 234, 0, 56, 193, 220, 190, 53, 21, 164, 74, 235, 198, 172, 125, 2, 17, 0, 0, 0, 7, 145, 225, 60, 4, 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