Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: db40a722446ce871395393b418f20d96016b873ed39a01934bd17062059b0147

Tx prefix hash: 86e1ddb98a8308b86a4276b769271927ba6d3878533eb72cdcb257f6f1b9269f
Tx public key: 5bce5aa9168bcc249727f23f6674f2171609e457db947b5c46e9462dd8303de6
Timestamp: 1697129684 Timestamp [UCT]: 2023-10-12 16:54:44 Age [y:d:h:m:s]: 01:102:12:00:20
Block: 868161 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 334459 RingCT/type: yes/0
Extra: 015bce5aa9168bcc249727f23f6674f2171609e457db947b5c46e9462dd8303de60211000000034b8f5122000000000000000000

1 output(s) for total of 0.815496772000 dcy

stealth address amount amount idx
00: b617451a91fee35f1cfb0e875d30f32c7dbdedee93b224bcbdd2032a754e45d6 0.815496772000 1322934 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": 868171, "vin": [ { "gen": { "height": 868161 } } ], "vout": [ { "amount": 815496772, "target": { "key": "b617451a91fee35f1cfb0e875d30f32c7dbdedee93b224bcbdd2032a754e45d6" } } ], "extra": [ 1, 91, 206, 90, 169, 22, 139, 204, 36, 151, 39, 242, 63, 102, 116, 242, 23, 22, 9, 228, 87, 219, 148, 123, 92, 70, 233, 70, 45, 216, 48, 61, 230, 2, 17, 0, 0, 0, 3, 75, 143, 81, 34, 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