Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 37cff523cf059ca9197a3d76feee54385f45fb1bf518e8b8c040906db9b3cc3d

Tx prefix hash: 02b554ac43d019e9df922b21ccc4fbad2a5db732231b7c1955a59bd202b7b4ad
Tx public key: 65717f6f9b054a55f232f6f690de16f904b8d3d79e6f8d82cfaeea5244b23bdc
Timestamp: 1661413082 Timestamp [UCT]: 2022-08-25 07:38:02 Age [y:d:h:m:s]: 02:219:22:49:04
Block: 573370 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 678422 RingCT/type: yes/0
Extra: 0165717f6f9b054a55f232f6f690de16f904b8d3d79e6f8d82cfaeea5244b23bdc02110000000cfaf35c9c000000000000000000

1 output(s) for total of 7.730138422000 dcy

stealth address amount amount idx
00: 0e2ccc80475d8cd6a0317bb088544e0f5c44c05a17385c41130bdfa4f8239bd9 7.730138422000 1006656 of 0

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": 573380, "vin": [ { "gen": { "height": 573370 } } ], "vout": [ { "amount": 7730138422, "target": { "key": "0e2ccc80475d8cd6a0317bb088544e0f5c44c05a17385c41130bdfa4f8239bd9" } } ], "extra": [ 1, 101, 113, 127, 111, 155, 5, 74, 85, 242, 50, 246, 246, 144, 222, 22, 249, 4, 184, 211, 215, 158, 111, 141, 130, 207, 174, 234, 82, 68, 178, 59, 220, 2, 17, 0, 0, 0, 12, 250, 243, 92, 156, 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