Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3270dd238b74f942ee9db10d089d017af47d037224fafb5e766ba63c9bf035d8

Tx prefix hash: adf9c4fe16a7f96af6999a74ca8890236fd8c8d407f23768da1f302b1b7fe413
Tx public key: 3fa7b1001565f8bf8fece7fe944dc005446c1283a19b82a33b4ad121ef1597d1
Timestamp: 1736271276 Timestamp [UCT]: 2025-01-07 17:34:36 Age [y:d:h:m:s]: 00:086:18:29:13
Block: 1192316 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 61796 RingCT/type: yes/0
Extra: 013fa7b1001565f8bf8fece7fe944dc005446c1283a19b82a33b4ad121ef1597d1021100000001007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e3ac86df5ca9ef82f10fdd58cd7c21eaa26b57e2976c08e906b316e66dc771c8 0.600000000000 1678865 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": 1192326, "vin": [ { "gen": { "height": 1192316 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e3ac86df5ca9ef82f10fdd58cd7c21eaa26b57e2976c08e906b316e66dc771c8" } } ], "extra": [ 1, 63, 167, 177, 0, 21, 101, 248, 191, 143, 236, 231, 254, 148, 77, 192, 5, 68, 108, 18, 131, 161, 155, 130, 163, 59, 74, 209, 33, 239, 21, 151, 209, 2, 17, 0, 0, 0, 1, 0, 127, 151, 138, 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