Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ac516ea033f18a486ab52db7429367608116fcd0e2ab49d2c33fb36f1ce5b67b

Tx prefix hash: ec7ff5d396f5dc21f9e5f9c4e08c716dd1317831b4e1a489f17c2a5553c75d60
Tx public key: 29b0fbeb1b78ece85f63115892b78edcb1ab8eb36d77f1c1ea2e6ae7c62307f9
Timestamp: 1713098021 Timestamp [UCT]: 2024-04-14 12:33:41 Age [y:d:h:m:s]: 00:316:23:31:31
Block: 1000317 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 226603 RingCT/type: yes/0
Extra: 0129b0fbeb1b78ece85f63115892b78edcb1ab8eb36d77f1c1ea2e6ae7c62307f902110000000452d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 911d50d630345ec1789712f4a85c5a95e015b222b3fe46631c38a5375b722736 0.600000000000 1460815 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": 1000327, "vin": [ { "gen": { "height": 1000317 } } ], "vout": [ { "amount": 600000000, "target": { "key": "911d50d630345ec1789712f4a85c5a95e015b222b3fe46631c38a5375b722736" } } ], "extra": [ 1, 41, 176, 251, 235, 27, 120, 236, 232, 95, 99, 17, 88, 146, 183, 142, 220, 177, 171, 142, 179, 109, 119, 241, 193, 234, 46, 106, 231, 198, 35, 7, 249, 2, 17, 0, 0, 0, 4, 82, 212, 126, 148, 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